Techniques and apparatus for editing video

ABSTRACT

An apparatus may include a memory to store a recorded video. The apparatus may further include an interface to receive at least one set of sensor information based on sensor data that is recorded concurrently with the recorded video and a video clip creation module to identify a sensor event from the at least one set of sensor information and to generate a video clip based upon the sensor event, the video clip comprising video content from the recorded video that is synchronized to the sensor event.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of, claims the benefit of andpriority to previously filed U.S. patent application Ser. No. 14/459,229filed Aug. 13, 2014, entitled “TECHNIQUES AND APPARATUS FOR EDITINGVIDEO”, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present embodiments are related to techniques for managing videocontent and to the creation and distribution of video clips.

BACKGROUND

Recording of video content is ubiquitous as the proliferation of devicesequipped with video recording capability expands to encompass portablecomputers, netbooks, tablet computers, cell phones, smart phones,phablets, wearable devices such as watches, glasses, and mountable videorecording device. Because of the increased density of recording media,and the ability to stream video efficiently between devices, evenrelatively small devices may be equipped to record large videos that mayconsume minutes of time or more.

However, such recorded videos may often remain unprocessed afterrecording due to the relatively cumbersome task of editing videocontent, which may be time consuming and may not be convenientlyperformed on many devices. Although professional editing may beperformed to produce a more enjoyable video content based uponuser-recorded video, the number of videos that are recorded by anamateur user and the expense associated with professional editing maypreclude this choice except in very special circumstances.

As a result, in a large number of instances, non-edited amateur videosthat are recorded in a wide variety of settings, such as sportingevents, holidays, gatherings, meetings, and the like, may accumulate andmay be rarely enjoyed after recording. It is with respect to these andother considerations that the present improvements may be needed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a block diagram of an automated video editing systemaccording to various embodiments.

FIG. 1B depicts a block diagram of an automated video editing systemaccording to various additional embodiments.

FIG. 1C depicts a block diagram of an automated video editing systemaccording to various additional embodiments.

FIG. 1D depicts a block diagram of operation of another automated videoediting system arranged in accordance with additional embodiments.

FIG. 2A depicts one additional embodiment of a video editing system.

FIG. 2B depicts another embodiment of a video editing system.

FIG. 3 illustrates an example of recorded activity.

FIG. 4 depicts one variant of a user device.

FIG. 5 depicts a block diagram of an automated video editing systemaccording to additional embodiments.

FIG. 6 depicts a sequence of operations involved for video clipgeneration when sensor events are detected based upon the architectureshown in FIG. 5.

FIG. 7 shows an exemplary first logic flow.

FIG. 8 shows an exemplary second logic flow.

FIG. 9 shows an exemplary third logic flow.

FIG. 10 illustrates an exemplary system architecture.

DETAILED DESCRIPTION

Embodiments provide enhancements for editing of videos. Consistent withvarious embodiments, systems, techniques and apparatus are provided thatenhance the editing of a video by employing sensor data that may becollected concurrently with the recording of the video. The sensor datamay be used to identify a sensor event or sensor events that form thebasis of generating a video clip or video clips.

Various embodiments exploit the capability of sensor technology that maybe deployed across a wide variety of components, both wearable andnon-wearable, in order to facilitate automated video editing. Inparticular various embodiments provide systems and methods to exploitsensor information that may be recorded, collected and synchronized witha concurrently recorded video to assist in editing that video. The term“video” as used herein may refer to a digital recording that contains avideo track, and may optionally include or be associated with otherrecorded data, such as an audio track. Unless otherwise noted, the term“video” (also referred to as “recorded video”) as used herein may alsorefer to recorded video that records live activity using a camera,sensor, or other detector, as opposed to a computer-generated video oranimation. In the context of the present embodiments, a video may berecorded in any suitable setting by any suitable recording deviceincluding a camera, dedicated video camera, computer, portable computer,tablet computer, cell phone, smart phone, phablet, wearable camera,other wearable device such as a head mounted device, digital watchdevice, or other device. The embodiments are not limited in thiscontext.

The present embodiments may provide a video clip creation module thatuses sensor information collected concurrently with video in order toidentify instances in a video from which to generate a video clip orvideo clips. The term “video clip” as used herein may refer to a portionof a recorded video that is less than the entire video, whose durationmay be a fixed duration or may be variable. In some instances theduration of a video clip may be on the order of several seconds, orseveral tens of seconds. However, the embodiments are not limited inthis context.

The present embodiments also provide systems and architecture thatfacilitate efficient computation to generate video clips. In someexamples, sensor information may constitute unanalyzed sensor data thatis collected concurrently with video from which video clips are to becreated. The unanalyzed sensor data may be received by a device thatrecords the video, such that the recording device may generate videoclips from the recorded video, either in real-time, or subsequent to therecording of the video. In other examples, sensor information mayconstitute sensor data that is collected concurrently with a video andis received and analyzed by a remote device such as a server. Theanalyzed data may transmitted to or retrieved by a user device, such asa device that records the video, or other user device. The sensorinformation may include at least one set of sensor information where aset of sensor information includes one or more items of sensorinformation. For example multiple sets of sensor information may becollected from multiple sensors concurrently with the recording of avideo. A given set of sensor information may be derived, for example,from a data stream composed of multiple items of data that is outputover time from a given sensor.

In various embodiments, a video clip creation module may be embedded inany convenient device such as a user device that records a video. Thevideo clip creation module may be used to identify a sensor event from aset of sensor information that is received by the user device and togenerate a video clip based upon the sensor event.

In some embodiments, a sensor event that triggers the generation of avideo clip may be identified in real-time during recording of video. Inother embodiments, the sensor event may be identified after-the-factbased upon recorded video and sensor information. In still otherembodiments, the occurrence of a sensor event may be used to guiderecording of a video in real time. As used herein, the term “sensorevent” refers to detected activity based upon sensor data other thanvideo Examples of sensors that may be employed in accordance with thepresent embodiments include accelerometers, gyrometers, positiondetectors, altimeters, audio detectors, proximity sensors such as radiofrequency or infrared proximity sensors, humidity sensors, or othersensors, that can detect characteristics of the environment, peoplenearby, the person recording and the devices. The embodiments are notlimited in this context. Examples of sensor events include a rapidchange in an accelerometer reading as a function of time, which may beindicative of a force experienced by a sensor. Other sensor events mayinclude a rapid change in altitude detected by an altimeter as afunction of time, a rapid change in audio intensity as a function oftime, and so forth. In various embodiments, a sensor event may becomposed of multiple changes that are detected by multiple differentsensors at the same time or closely spaced in time, such as two eventsthat occur within several seconds of one another. In addition, a sensorevent may have other information associated with the sensor event, suchas a time stamp and information concerning an object or entity thattriggered the sensor event.

The sensor event may occur during the concurrent recording of video suchthat the sensor event may be temporally correlated or synchronized withthe video. Synchronization may be facilitated, for example, with the aidof time stamps that are provided with recorded sensor data and recordedvideo. For example, sensor data may be recorded and stored with a timestamp for each item of recorded sensor data. The time stamp associatedwith a given sensor event may then be used to synchronize with videowhich may be recorded with its own time stamp, so that a portion ofvideo that is recorded during a given sensor event may be identified. Invarious embodiments sensor data and video from the different componentsused to record video and sensor data may be synchronized according toknown protocols such as network time protocol (NTP).

As detailed below, in accordance with various embodiments, adetermination may be made as to whether and how to generate a video clipfrom a recorded video based upon a sensor event.

FIG. 1A illustrates a block diagram of an automated video editing system100 according to various embodiments. The automated video editing system100 provides a general architecture that may be implemented in differentmanners to automatically generate video clips from recorded video. Asillustrated, a video clip creation module 108 may receive inputs fromvarious components. A video source 102 may provide video to the videoclip creation module either in real time or subsequent to recording ofthe video. The video source 102 may be a video recording device in someimplementations, but may also be a device that stores video recorded bya separate device. Sensors 104 may include at least one sensor that isnot a video recording device as noted above. The sensors 104 may providesensor information to the video clip creation module 108 that is used toassist in automated video editing of a given video, such as thegeneration of at least one video clip from the video supplied by videosource 102. User interface inputs 106 may also be provided to the videoclip creation module 108 to assist in video editing as detailed below.

It is to be noted that the video clip creation module 108 and othersimilar components as disclosed below, may comprise various hardwareelements, software elements, or a combination of both. Examples ofhardware elements may include devices, components, processors,microprocessors, circuits, circuit elements (e.g., transistors,resistors, capacitors, inductors, and so forth), integrated circuits,application specific integrated circuits (ASIC), programmable logicdevices (PLD), digital signal processors (DSP), field programmable gatearray (FPGA), memory units, logic gates, registers, semiconductordevice, chips, microchips, chip sets, and so forth. Examples of softwareelements may include software components, programs, applications,computer programs, application programs, system programs, machineprograms, operating system software, middleware, firmware, softwaremodules, routines, subroutines, functions, methods, procedures, softwareinterfaces, application program interfaces (API), instruction sets,computing code, computer code, code segments, computer code segments,words, values, symbols, or any combination thereof. Determining whetheran embodiment is implemented using hardware elements and/or softwareelements may vary in accordance with any number of factors, such asdesired computational rate, power levels, heat tolerances, processingcycle budget, input data rates, output data rates, memory resources,data bus speeds and other design or performance constraints, as desiredfor a given implementation.

The video clip creation module 108 may be coupled to a communicationssystem 110. As detailed below an output of the video clip creationmodule 108 may be at least one video clip that is excerpted from a videoprovided by the video source 102. As detailed below a video clipgenerated by the video clip creation module 108 may be sent via thecommunications system 110 to various destinations. These destinationsmay include a user device that records video from which the video clipis created, a specific external device or devices, or may be a cloudstorage destination, where cloud storage represents storage of user datathat may span one or more locations and may be controlled by one or morecomputers that are hosted via a third party and are accessible to theuser via a network such as the Internet. In some examples, a destinationor destinations for receiving a video clip may be determined from userinterface inputs 106.

In some embodiments, a cloud/server infrastructure may be provided thatis coupled to sensors whose sensor data is to be used to generate videoclips from a video. FIG. 1B depicts a block diagram of an automatedvideo editing system 114 according to various additional embodiments.The automated video editing system 114 provides a general architecturethat may be implemented in different manners to automatically generatevideo clips from recorded video. As illustrated, automated video editingsystem 114 may include those components as described above with respectto FIG. 1A. However, the architecture of automated video editing system114 also includes a cloud/server system 116, which may include variousstorage, communications, and data processing components that arearranged in a cloud architecture. As illustrated, the sensors 104 arelinked to the cloud/server system 116. The sensors 104 may providesensor information to the cloud/server system 116 that is used to assistthe video clip creation module 108 in automated video editing of a givenvideo, as described in more detail below. The cloud/server system 116may output, for example, sensor information that includes analyzedsensor data to aid the video clip creation module 108 in identifying asensor event that triggers creation of a video clip.

In the example of FIG. 1B a video clip creation module 108 is linked tothe cloud/server system 116 to receive analyzed sensor information, forexample, but not directly linked to sensors 104. However, in otherexamples, a video clip creation module 108 may be linked directly toboth a cloud/server system 116 and to sensors 104. FIG. 1C depicts ablock diagram of an automated video editing system 118 according tovarious additional embodiments. The automated video editing system 118provides a general architecture that may be implemented in differentmanners to automatically generate video clips from recorded video. Asillustrated, automated video editing system 118 may include thosecomponents as described above with respect to FIG. 1A and FIG. 1B.However, in the embodiment of FIG. 1C the video clip creation module 108is linked both to the sensors 104 and the cloud/server system 116. Inthis implementation, the video clip creation module 108 may receivesensor data directly from sensors 104 and may also receive sensorinformation that includes analyzed sensor data from the cloud/serversystem 116.

In some embodiments, sensors that provide inputs to a video clipcreation module may be distributed across multiple wearable andnon-wearable components. For example, in a given environment in which avideo is recorded multiple wearable and non-wearable sensors may belinked to a device to receive sensor information to be exploited by thevideo clip creation module to create a video clip. FIG. 1D depicts ablock diagram of operation of another automated video editing system 120arranged in accordance with additional embodiments. As illustrated,recorded activity 122 may represent any activity that is recorded by adevice such as a video recording component 124. The recorded activity122 may be a sporting event, a musical event, leisure activity, or otheractivity. The video recording component 124 may record video content 144from the recorded activity 122, which may be composed of a video trackand audio track in some embodiments. A wearable sensor 126 may recordwearable sensor data 146, which in one example may be altimeter data. Anobject sensor 128 may record object sensor data 148, which in oneexample may be accelerometer data. The video recording component 124 mayoutput a video 154, which includes a video track and a video track timestamp, for example. A video track time stamp may include a time entryfor every video frame of a video track in one example. The wearablesensor 126 may output a sensor data stream 156, which may includealtitude data recorded by the wearable sensor 126 as a function of time,as well as a time stamp in which each altitude data entry is associatedwith a time entry of the time stamp. The object sensor 128 may outputsensor data stream 158 which may include accelerometer data recorded bythe object sensor 128 as a function of time, as well as a time stamp inwhich each accelerometer data entry is associated with a time entry ofthe time stamp.

In operation the video clip creation module 108 may receive the video154, sensor data stream 156, and sensor data stream 158, and maygenerate video clip output 160, which is composed of at least one videoclip. The video clip output 160 may in particular include a given videoclip having a duration of, for example, one second, five seconds, sixseconds, or other duration. The video clip generation module 108 mayselect the given video clip based upon a sensor event that is determinedfrom the sensor data stream 156, sensor data stream 158, or both sensordata stream 156 and sensor data stream 158. Details of determination ofa sensor event are provided in the discussion to follow.

After generating video clip output 160, the video clip creation module108 may send the video clip output 160 to various destinations, such asa local memory 130 that is resident on a device that contains the videoclip creation module 108, or to cloud storage 132, or to an externaldevice 134. The determination of destinations to receive video clips isalso described in more detail below. In various embodiments, video clipoutput 160 may be generated in real time as a video 154 is beingrecorded, while in other embodiments video 154 may be processed by avideo clip creation module 108 at a time subsequent to when the video154 is recorded.

In some embodiments a device that is used to record video may alsogenerate video clips from the recorded video either in real-time orsubsequent to recording of the video. FIG. 2A depicts one embodiment ofa video editing system 200 that includes a user device 202, which isused as a video recording device. For example, the user device 202 maybe a video camera, cell phone, smartphone, tablet computer, wearabledevice, phablet, or other device. In the example of FIG. 2A, the userdevice 202 includes a video recording component 124 that is used torecord video content 220 from the recorded activity 122. Video 206 thatincludes the video content 220 and a time stamp may be stored locally,for example, in memory 212. Over a same period as user device 202records video content 220, sensors 204 may record sensor data 222 fromthe recorded activity 122. The sensors 204 may output sensor information208 that includes a time stamp for the sensor data 222. The user device202 may include a communication component 214 that is operative toreceive sensor information 208 over a link 210, which may employ a knownwireless technology in some embodiments. The sensor information 208 andvideo 206 may be transmitted to the video clip creation module 108,which generates video clip output 224. As illustrated, the video clipoutput 224 may be stored in the memory 212. The video clip output 224may also be distributed to other destinations, as illustrated, forexample, in FIG. 1B.

In some embodiments separate logic or circuitry, such as processor 216,may be operative on the video clip generation module 108 to assist ingeneration of the video clip output 224, as well as the distribution ofvideo clip output 224. As illustrated in the embodiment of FIG. 2A theprocessor 216 may operate locally within the user device 202. However,in other embodiments, a processor or other logic that assists in videoclip generation, for example, may be located remotely from the userdevice 202, and may be located remotely from the video clip generationmodule 108. In such circumstances the processor may perform certaintasks that assist in determining a sensor event as detailed below.

As further shown in FIG. 2A the user device 202 includes a userinterface 118, which may include a mouse, keyboard, keypad, voiceinput/output, touchpad, or touch screen, or other known component. Theuser interface 118 may transmit input to the video clip creation moduleto assist in generation of the video clip output 224, as well as thedistribution of video clip output 224.

FIG. 2B depicts another embodiment of a video editing system 250 thatincludes a user device 252 and may include similar components to thoseof user device 202. However, in the video editing system 250 the sensors204 are coupled to an external processor 254 located in the cloud/serversystem 116 to send the sensor data 208, which is analyzed by theexternal processor 254. The external processor 254 may then forwardsensor information 256 over a link 257 to the user device 202, in whichthe sensor information 256 represents a result of analysis of the sensordata 208. The sensor information 256 and sensor data 208 may be receivedby video clip creation module 108, which generates video clip output258.

For the purposes of illustration, in figures to follow there isillustrated one scenario for implementing automated video editing inaccordance with embodiments of the disclosure. Turning now to FIG. 3,there is shown an example of recorded activity 302. In the particularexample illustrated, the recorded activity 302 constitutes a basketballgame. During the basketball game multiple users may employ devices torecord video. In some cases, users may record minutes or even hours ofvideo to document the basketball game. In order to assist users togenerate short excerpts or video clips from that may present moreinteresting instances of action within a recorded video, an array ofsensors may be deployed in the basketball arena. For example, wearablesensors may be worn by basketball players participating in thebasketball game in order to record features such as movement,acceleration, orientation, location, or sound. In addition, fixedobjects or movable objects may be equipped with sensors to record theaforementioned features or other features.

In the instance shown in FIG. 3, a player 304 grasps the basketball 306and may be in the process of attempting to score at the basket 308. Aball sensor 310 is embedded in the basketball 306 and may record ballmovement, acceleration, or location, for example. A hoop sensor 312 isaffixed to the basket 308 and may record acceleration or force. A wristsensor 314 is worn by player 304, which may detect motion, acceleration,orientation, or location. Similarly, a shoe sensor 316 is embedded inone or both shoes of the player 304, which may also detect motion,acceleration, orientation, or location. All of these sensors may beconfigured to collect sensor data and transmit that data, for example,by wireless transmitters that are collocated with the respectivesensors. In one implementation, the sensor data recorded from thedifferent sensors may be transmitted in real-time as the sensor data isrecorded.

As further illustrated in FIG. 3, a user device 318 may record videofrom the basketball game. In one implementation, the user device 318 mayalso be configured to wirelessly receive sensor data generated by thewrist sensor 314, shoe sensor 316, hoop sensor 312, and ball sensor 310.In one particular example, the user of user device 318 may be a parentof the player 304 and may record a portion of the basketball game as avideo. At the instance in time depicted in FIG. 3, the player 304 maycomplete a particularly nice layup that is recorded as a sensor event bythe wrist sensor 314, shoe sensor 316, hoop sensor 312, and ball sensor310. For example, at least one of the wrist sensor 314, shoe sensor 316,hoop sensor 312, or ball sensor 310 may register a large change insensor data at the time the layup is completed. In one example, anaccelerometer embedded in the shoe sensor 316 may record a spike, thatis, an abrupt change, in acceleration that is indicative of a forceduring the layup. In one example, an accelerometer embedded in the shoesensor 316 may record a spike, that is, an abrupt change, indicating anincreased force experienced by the shoe sensor 316 during the layup.Similarly, an accelerometer embedded in the ball sensor 310 may alsorecord an acceleration spike when the ball 306 hits the basket 308 or abackboard (not shown). In addition, a motion detector in the hoop sensor312 may record a spike when the ball 306 strikes the basket 308.

Because each sensor may be configured to transmit sensor data with atime stamp, an instance in time associated with each sensor eventrecorded by a respective sensor may be provided to a device that is incommunication with the sensors. Each of these individual sensor eventsmay be recorded and time stamped so that an instance when the ballsensor 310, hoop sensor 312, wrist sensor 314 and shoe sensor 316 detectrespective sensor events can be determined. In one implementation theuser device 318 may be configured substantially the same as user device202 to include a video clip creation module 108. The user device 318 maytherefore receive respective time stamped sensor information from theball sensor 310, hoop sensor 312, wrist sensor 314, and shoe sensor 316,and may analyze the received time stamped sensor information.

In addition, each sensor may have a unique identification that thelocation of each sensor or object or person associated with each sensormay be tracked, either by a sensor itself or by another entity such as acloud based entity.

In one instance where the ball sensor 310, hoop sensor 312, wrist sensor314, and shoe sensor 316 each generate sensor data spikes, such asacceleration spikes that are indicative of forces being experienced, theuser device 318 may determine that multiple sensor events have occurred,and may determine that the multiple sensor events are closely spaced intime. The user device 318 may therefore determine that a video clip isto be created from video that is concurrently recorded by the userdevice 318, where the video clip is generated from a portion of therecorded video whose time stamp is closely synchronized with thereceived sensor events. For example, if the sensor events occur within agiven two second time span at 2:15 in the second quarter of thebasketball game, the user device 318 may generate a six second videoclip that begins at 2:12 of the second quarter and ends at 2:18 of thesecond quarter in order to capture video that coincides with thedetermined sensor events. In this manner the user device 318 mayautomatically generate a video clip that encompasses the time frame inwhich the layup by player 304 takes place.

In other embodiments a video clip may be generated based on anypredetermined relation to a time stamp of a sensor event. For examplethe video clip may be configured to start at a time corresponding to thetime stamp of the sensor event or to overlap the time stamp so that thesensor event time stamp is in the middle of the video clip.

In one particular embodiment, the user device 318 may be configured toautomatically send video clips that are created to designated target(s).Moreover, the user device 318 may further be configured to determinewhen to generate a video clip based upon a predetermined criteria suchas stored information in the user device 318 or based upon user inputreceived by the user device 318.

In one example, each wearable sensor that is deployed on a basketballplayer may have a unique identifier that is transmitted together withsensor data to identify the sensor and thus may identify the player 304to a receiving device. Accordingly, the user device 318 may beconfigured to generate a video clip when a sensor event associated withthe wrist sensor 314 of shoe sensor 316 is received. For example, aparent of the player 304 who operates the user device 318 may configurethe user device 318 to generate a video clip and forward to otherdevices such as to a device of a parent that is absent from thebasketball game.

It is to be noted that in the scenario of FIG. 3 multiple users mayoperate multiple different video recording devices to record the samebasketball game, such as recording device 320 and recording device 322.The recording device 320 and recording device 322 may further beconfigured to receive sensor information transmitted from sensorsdeployed in the basketball arena depicted in the scene of recordedactivity 322. However, the recording device 320, may be configureddifferently than user device 318, such that when the recording device320 receives the same set of sensor events as received by the userdevice 318, the recording device 320 may or may not generate a videoclip. For example, the operator of recording device 320 may be theparent of a different player (not shown) than player 304, and mayconfigure the operating device 320 to generate a video clip when sensorevents associated with wearable sensors worn by the different player arereceived, but not when sensor events associated with wrist sensor 314 orshoe sensor 316 are received. Accordingly, at 2:15 in the second periodwhen the action depicted in FIG. 3 takes place, a video clip creationmodule 324 resident on the operating device 320 may determine that novideo clip is to be generated based upon the sensor events detected at2:15 in the second period or thereabouts.

It is to be noted that in the scenario of FIG. 3 that the videorecording apparatus may be installed within the venue generally depictedin the recorded activity 302. In this manner, video and sensor data maybe stored in a server that subsequently creates and distributes videoclips to interested parties. For example, the fans of one player mayrequest just the video clips that depict when that player scored.

In additional embodiments a user interface located on a user device maybe configured to present indicators of a sensor event. FIG. 4 depictsone variant of the user device 318 in which the user device 318 is asmartphone that includes a display 402. Within the display 402 there maybe presented the images of video being recorded as well as a video clipregion 404 that presents a snapshot composed of a video frame thatrepresents an instance in time for which a video clip has been created.The video clip region 404 may be updated in real-time as additionalvideo clips are created.

Although the aforementioned scenario involves the generation of a videoclips based upon sensors associated with a single player, in otherembodiments, any number or sensors may be monitored that are deployed onany number of players or objects in order to automatically edit video.The automated generation of video clips may be based upon any number ofsensor events as well as heuristics which may be associated with aparticular activity such as a basketball game. In various embodiments avideo clip generation module may be configured to generate a video clipbased upon whether certain correlation criteria are met betweendifferent sensor events. For example, correlation criteria may includetemporal correlation of sensor events, spatial correlation of sensorevents, or both, among other possible correlations. The temporalcorrelation of sensor events may refer to the time interval betweensensor events. The spatial correlation of sensor events may refer tospatial proximity between sensors that generate different sensor events.For example, in a basketball game in which multiple players areoutfitted with wearable sensors, a video clip generation module mayattribute an action to a particular player based upon the timing ofdifferent sensor events that are received from different players, andobjects, such as a basketball.

FIG. 5 depicts a block diagram of an automated video editing system 500according to additional embodiments. In this example, an architecture isshown that involves multiple different players having wearable sensorswhose sensor information may be monitored to assist in video clipcreation. A user environment 502 includes object sensors 504, which mayinclude sensors embedded in or attached to movable objects or fixedobjects. In the example of a basketball game the object sensors mayinclude sensors embedded in a basketball and in basket. The userenvironment 504 further includes first player wearable sensors 506 andsecond player wearable sensors 508, each of which may be attached torespective first and second players. The user environment 502 may alsoinclude environmental sensors 510. All of these sensors may providesensor data to the video clip creation module 512, which may be embeddedin a video recording device in one example that records video in theuser environment 502.

FIG. 6 depicts a sequence of operations involved in which a video clipis generated when sensor events from multiple different players aredetected based upon the architecture shown in FIG. 5. At operation 602,wearable sensors on a first player are monitored. The sensors maygenerate sensor data that indicates force or acceleration associatedwith the first player as a function of time. At operation 604, wearablesensors of a second player are monitored. At operation 606 objectsensors are monitored, such as a basketball sensor. The basketballsensor may generate sensor data that indicates forces experienced by thebasketball as a function of time. At operation 608 a basket sensor ismonitored. The basket sensor may be sensitive to events such as when abasketball or player contacts the rim of the basket, which may generateforces that are registered by the basket sensor.

At operation 610 an indication of scoring is received. For example, thebasketball sensor, the basket sensor, or both sensors may generatesensor data that indicates a force associated with an instance when abasketball interacts with the basket or backboard.

At operation 612 the detected scoring is attributed to the first player.For example, the scoring may be attributed to the first user based uponthe timing of forces that are measured from the different sensor eventsregistered from wearable sensors on the first player and on the secondplayer, as well as forces registered by the basketball and basket.

At operation 614 a video clip time range is determined, which may bebased upon the time stamp of the detected scoring and the attribution ofscoring to the first user. The video clip time range may further bedetermined based upon user preferences that may be entered in a userdevice associated with a video clip generation module.

At operation 616 a video clip is generated which is excerpted from avideo being recorded within the video clip time range. At operation 618,the video clip generated in operation 616 is shared with otherdestinations.

In summary the present embodiments provide multiple advantages incomparison to current technology where convenient tools for editingvideo are lacking. By providing automated identification and generationof video clips including the generation of video clips in real-timeduring recording of a video many additional scenarios and capabilitiesare enabled. For one, video content may be automatically edited based onsensed events and heuristics where the ability to determine when togenerate a video clip can be improved over time by a video clipgeneration module.

In addition, various embodiments facilitate attribution of a sensorevent to a user (player) based upon multiple sensors. In one example,wearable force sensors may be analyzed in concert with sensor-embeddedtools and objects that are not assigned to a single user, such asembedded sensors in a ball. A combination of sensor events detected froma ball sensor and wearable sensors on a user may then be employed todetermine when that user contacted the ball.

In particular scenarios, an action on an object such as a ball may beattributed to a first player as opposed to a second player based uponthe timing of spikes in forces (sensor events) experienced by the objectand by wearable sensors on the first player and second player, asoutlined above with respect to FIG. 6.

In addition, the present embodiments facilitate automatic communicationof video clips to target destinations, which may include a variety ofother people and systems in addition to a user device that generates thevideo clip. In some embodiments, social networking or email applicationsmay be employed according to user preferences in a user device to setdestinations for distributing a video clip. Destinations may includeobjects such as wearable displays, scoreboards or other devices that maybe useful for presenting the video clips. In other embodiments,automatically generated video clips may also be automatically sent to ahost in a social network previously chosen by a sensor wearer and/or bya person or system that records the video from which the video clips arecreated. For example, video clip creation module may be coupled to amemory or program that stores user inputs and directs video clips to aset of one or more destinations including a social media site. In thiscontext automatic posting of a video clip may be directed to a hostedsocial media site that is publically accessible according to knownmethods so that those viewers with access to the social media site mayinstantly view a video clip after creation. In one example, the socialmedia site may be hosted by a server or group of servers that areaccessible via a data network, such as the Internet.

In one implementation, an automated video editing system may designatemultiple persons may of interest for a particular video clip, such thatmultiple persons may freely engage in a social network to defineinterest in an object or person that is also tracked by a person filmingan event.

In other implementations, an automated video editing system may be usedto automatically generate video clips for presentation in conjunctionwith instant replay in broadcast sporting events. Based upon individualsensors associated with a given player, video clip generation may betargeted for that given player.

In additional implementations, contextual analysis may be performed, forexample, to automatically determine when to generate video clips and toautomatically determine destinations for a generated video clip. Invarious embodiments a video clip generation module may determine asource of sensor information that results in a sensor event thattriggers creation of a video clip, and may schedule transmission of thevideo clip to a target destination at a remote location based upon thesource of the sensor information. For example, it may be determined thata given sensor wearer is the source of a sensor event. One parent of asensor wearer may be present at a game, who may be a user associatedwith a user device that records the video and generates the video clip.A user device or a server/cloud system may also determine using knowntechnology that a second user device associated with a second parent ofthe sensor wearer is not present at the game. Accordingly, when a videoclip is generated based upon action(s) of the sensor wearer, the videoclip may be automatically forwarded to a target destination such as thesecond user device associated with the absent parent.

Another example of contextual analysis is the use of factors such as thetime of day or type of activity being recorded as to whether to activatevideo clip generation. For example, in an automated video editing systemthat is deployed to record public events, such as a sports arena, videoclip generation may be triggered according to the time of day, which maycorrespond to the time for a particular event, or could be triggeredbased upon the type of activity being recorded, such as a basketballgame as opposed to running activity.

Moreover, the present embodiments may exploit a wide range of differenttype of sensor events to automatically generate video clips beyond thosehighlighted above. In some implementations, in addition to detection ofphysical activity such as jumping, the proximity of persons to otherpersons or proximity to objects may be registered as sensor events andused to automatically create a video clip. In additional embodiments,biosensors may be monitored to measure, for example, excitement level ina wearer of the biosensor in order to assess the involvement of thewearer in a particular action. If at a given instances the excitementlevel exceeds a certain threshold, a video clip excerpted from videosynchronized to that instance may be generated.

Moreover, in some implementations, sensor activity or detected sensorevents based upon sensor location, proximity, or force, as well asprevious history of sensor data, may be used to proactively predict anactivity to be captured in a video. For example, a video clip generationmodule or related logic may identify a sensor event based upon sensordata received from proximity sensors and accelerometers, and maydetermine that a certain sequence of events is underway. The video clipgeneration module may subsequently generate a signal to “recommend” to auser of a video recording device to move the recording device to capturein video a predicted activity. For example, the video clip generationmodule may generate a signal to move a video recording device to theright based upon a predicted kick or throw that is to take place in ascene being recorded by the video recording device, or may direct avideo recording device to orient toward a region where greater action istaking place based upon sensor events recorded from multiple differentsensors, such as players in a playing field or court. In some particularexamples, haptic feedback may be provided to a user of a recordingdevice to proactively direct actions to be performed by the recordingdevice.

The automated video editing systems provided by the present embodimentsalso provide in real-time information that is needed to determine the“interestingness” of a particular video clip.

In particular examples, an automated video editing system may employuser preferences and heuristics to set the “interestingness” of a videoclip or set of video clips to be stored, presented, or distributed to adestination. The user preferences or user criteria may also be used toset a duration of a video clip as well as to synchronize the video clipwith a detected sensor event. An example of a user criterion includes:provide a video clip for five seconds before a certain individual scoresa basket and three seconds after the basket is scored. In this example,a video clip generation module may set a predetermined relation betweena time stamp of a detected sensor event that is identified as a basketand a video clip to be generated from a video recorded concurrently withthe detected sensor event. Thus, when the video is synchronized to adata stream representing a detected sensor event, a video clip may begenerated that spans a duration between five seconds before an instancein time of the video that corresponds to the instance of the sensorevent and three seconds after the instance in time.

In other examples, a user may set a specific user criterion or criteriato decide whether to retain a generated video clip or whether togenerate a video clip based on a sensor event. The user criterion maybe, for example, to just retain a video clip based on when an individualinteracts with certain objects, or when a sensor event corresponds towhen a sensor wearer is jumping, or running fast, or theexcitement/stress level is high.

The receipt of user preferences or user criteria to manage video clipsmay take place over any convenient user interface, which may be a voiceactivated interface or touch sensitive interface in some embodiments.For example, in reference to video clips of a given basketball player, auser may say, “Give me a highlight clip of Dawn that shows her fivehighest jumps,” or “Make a one-minute highlight clip of Dawn's scores.”If in one scenario Dawn scored 6 times, the automated video editingsystem may use an average of 10 seconds per score to generate a videoclip highlight. Some of the video clips may be arranged to be longerthan others, e.g., if Dawn had possession of the basketball for anextended period before scoring.

It is to be noted that various embodiments as discussed above allow thecomputation involved in automated video editing to be split betweendifferent entities, such as between a server/cloud system and a mobiledevice that houses a video clip creation module. This provides a furtheradvantages that computation performed by a user device to generate agiven video clip or video clips may be reduced, while still preservingthe ability of a user device to tailor video clip generation to userpreferences. For example, in a scenario of a given sporting event inwhich multiple recording devices are employed to record video, at leastsome of the recording devices may be equipped with video clip creationmodules to automatically create video clips based upon video beingrecorded at the sporting event. During the sporting event multipledifferent recording devices may capture a record of the same action,albeit from slightly different points of view. However, action that isinteresting for a user of a first device, whose relative is involved inscoring a basket or other actions, may not be of interest to otherspectators who are recording the sporting event for other reasons. Inaddition, recorded material from a first user may be of interest to asecond user so that sharing of content from the first user may aid thesecond user in obtaining desired video clips. Accordingly, anarchitecture such as presented in the automated video editing system 114or the automated video editing system 118 may be employed to splitcomputation involved in generation of video clips between a server/cloudsystem and a user device that houses a video clip creation module.

In one implementation, a server/cloud system may centralize commoncapabilities that are useful for generation of video clips. For example,the server/cloud system may be employed to receive sensor data from atleast one sensor that is deployed at a recorded activity, and mayperform calculations to make initial inferences, such as what person isperforming a given action, what objects are involved, and so forth.These initial inferences may be forwarded to receiving user devices asanalyzed data. The analyzed data may then be used by individual userdevices to determine whether and how to create a video clip based uponuser-specific inference and algorithms that are employed by the videoclip creation module on the user device.

Thus, multiple different user devices at a sporting event may record avideo that captures a first player scoring a basket. This action may beanalyzed by a server/cloud infrastructure as a possible sensor eventfrom which to generate a video clip, such that the analyzed data istransmitted to user devices coupled to the server/cloud system. Theanalyzed data may include indicia that indicate identity of the firstplayer involved in scoring the basket in one example. A user device ofthe relative of the first player may be configured to automaticallygenerate a video clip based upon a detected sensor event associated withthe first player, while other user devices may be configured create avideo clip based upon a detected event when other criteria are met.Accordingly, the same instance of scoring by the first player maytrigger automatic creation of a video in some user devices but notothers, all of which user devices may be recording the same or similarvideo. At the same time the amount of computation performed locally on auser device may be reduced since the user device is not required to makean initial determination, for example, as to the occurrence of a sensorevent or as to the identity of a person associated with the sensorevent.

In various additional embodiments, the partitioning of computationinvolved in automated generation of video clips between a local userdevice and a server/cloud system may be varied. In one example completecomputation for automated generating of video clips may be performed ina cloud/server system, while in another example, complete computationfor automated generating of video clips may be performed in a userdevice.

Included herein is a set of flow charts representative of exemplarymethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, for example, in the form of a flowchart or flow diagram, are shown and described as a series of acts, itis to be understood and appreciated that the methodologies are notlimited by the order of acts, as some acts may, in accordance therewith,occur in a different order and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all acts illustrated in a methodology maybe required for a novel implementation.

FIG. 7 illustrates an exemplary first logic flow 700. In some examples,the logic flow 700 may be implemented in a user device that isconfigured to record a video. At block 702 recorded video is received.The recorded video may be received in real-time such that a firstportion of the recorded video is received while a second portion isbeing recorded or is yet to be recorded.

At block 704, sensor information is received that is based on sensordata measured concurrently with the recording of the recorded video. Inone example the sensor information may be a sensor data stream that isreceived from a sensor in real time as the sensor data is beingmeasured.

At block 706 a sensor event is identified from the received sensorinformation. The identification of a sensor event may be based upon anysuitable criterion related to the sensor information such as a change ina value of sensor data as a function of time. The sensor event may betime stamped such that a sensor event time stamp indicating the time atwhich the sensor event occurs is provided in the sensor information.

At block 708, the sensor event is synchronized with the recorded video.For example the recorded video may include a video track time stamp thatis used to synchronize the video to the sensor event by identifying aninstance in the video that corresponds to the sensor event time stamp.

At block 710 a video clip is generated based upon the sensor event. Thevideo clip may be created from a portion of the recorded video thatoverlaps the sensor event time stamp, for example.

FIG. 8 illustrates an exemplary second logic flow 800. In some examples,the logic flow 800 may be implemented in a user device that isconfigured to record a video. At block 802 a sensor data stream ismonitored during recording of a recorded video. The sensor data streambeing monitored may be produced by a sensor such as a wearable sensor orobject sensor or environmental sensor, to list a few examples.

At block 804 an indication of a sensor event is received based upon themonitored sensor data stream. The indication of a sensor event may bereceived from an external device such as a cloud server, or may begenerated by a user device that records the video.

At block 806 a user criterion is retrieved that is associated with thesensor event. For example, the sensor event may be determined from adata stream produced by a wearable sensor worn by a known person. A usercriterion may set a threshold for a sensor event based on the actions ofthe known person, such as the speed of movement, or level of excitementas determined in the sensor event.

At decision block 808 a determination is made as to whether the usercriterion is met. If not the flow returns to block 802. If so, the flowproceeds to block 810. At block 810 the sensor event is synchronizedwith the recorded video to determine a video track time stampcorresponding to the sensor event. The flow then proceeds to block 812in which a video clip is generated based upon the video track timestamp. The flow subsequently moves to decision block 814.

At block 814 a determination is made as to whether the video iscomplete, such as whether recording has stopped. If not the flow returnsto block 802. If so the flow ends.

FIG. 9 illustrates an exemplary third logic flow 900. At block 902,multiple sensor data streams are monitored during recording of a video.

At block 904, an indication of a first sensor event is received thatcorresponds to a first sensor. At block 906 an indication of a secondsensor event is received that corresponds to a second sensor differentfrom the first sensor. The first and second sensor may be located withina field of view that is recorded in the video at least during portionsof the recording of the video. The flow then proceeds to decision block908.

At decision block 908 a determination is made as to whether a set ofcorrelation criterion is met. The set of correlation criterion mayinclude at least one correlation criterion such as a criterion relatedto temporal correlation between the first sensor event and second sensorevent. One particular example of a correlation criterion may be athreshold of elapsed time between the first sensor event and secondsensor event. If the elapsed time between first sensor event and secondsensor event fall below a threshold, the correlation criterion may bedeemed to be met. Additionally a correlation criterion may be composedof a computed correlation coefficient between data sets, or numbersderived from the data sets, from two or more sensors. A chosen level forcorrelation coefficient value may be chosen to be the threshold. Invarious additional embodiments, various mathematical treatments may beused to form the basis of a correlation criterion, such as partialcorrelations, semi-partial correlations, and multiple regressionanalysis. In some instances, data from one or more sensors may be usedas a covariate as part of the analysis.

If not, the flow returns to block 902. If so, the flow proceeds to block910. At block 910 a video clip is generated based upon the first sensorevent and second sensor event. The video clip may be synchronized tooverlap in time the first sensor event and second sensor event in oneexample.

The flow then proceeds to decision block 912 where a determination ismade as to whether the recording of the video is complete. If not, theflow returns to block 902. If so, the flow ends.

FIG. 10 is a diagram of an exemplary system embodiment and inparticular, FIG. 10 is a diagram showing a system 1000, which mayinclude various elements. For instance, FIG. 10 shows that system(platform) 1000 may include a processor/graphics core, termed hereinprocessor 1002, a chipset/platform control hub (PCH), termed hereinchipset 1004, an input/output (I/O) device 1006, a random access memory(RAM) (such as dynamic RAM (DRAM)) 1008, and a read only memory (ROM)1010, display electronics 1020, display backlight 1022, and variousother platform components 1014 (e.g., a fan, a crossflow blower, a heatsink, DTM system, cooling system, housing, vents, and so forth). System1000 may also include wireless communications chip 1016 and graphicsdevice 1018, non-volatile memory port (NVMP) 1024, and antenna 1026. Theembodiments, however, are not limited to these elements.

As shown in FIG. 10, I/O device 1006, RAM 1008, and ROM 1010 are coupledto processor 1002 by way of chipset 1004. Chipset 1004 may be coupled toprocessor 1002 by a bus 1012. Accordingly, bus 1012 may include multiplelines.

Processor 1002 may be a central processing unit comprising one or moreprocessor cores and may include any number of processors having anynumber of processor cores. The processor 1002 may include any type ofprocessing unit, such as, for example, CPU, multi-processing unit, areduced instruction set computer (RISC), a processor that have apipeline, a complex instruction set computer (CISC), digital signalprocessor (DSP), and so forth. In some embodiments, processor 1002 maybe multiple separate processors located on separate integrated circuitchips. In some embodiments processor 1002 may be a processor havingintegrated graphics, while in other embodiments processor 1002 may be agraphics core or cores. Commands can be provided to processor 1002, forexample, through keyboard, touch screen interaction, gestures, facialexpressions, and sounds.

The following examples pertain to further embodiments. In example 1 anapparatus may include a memory to store a recorded video; an interfaceto receive at least one set of sensor information based on sensor datathat is recorded concurrently with the recorded video; and a video clipcreation module to identify a sensor event from the at least one set ofsensor information and to generate a video clip based upon the sensorevent, where the video clip comprises video content from the recordedvideo that is synchronized to the sensor event.

In example 2, the sensor information of example 1 may include analyzedsensor data calculated from the sensor data.

In example 3, the video clip creation module of any of examples 1 to 2may be to identify a multiplicity of sensor events from the sensorinformation and to generate a respective multiplicity of video clipsfrom the recorded video that are synchronized to the respectivemultiplicity of sensor events.

In example 4, the video clip creation module of any of examples 1 to 3may be to identify a first time stamp of sensor data associated with thesensor event and generate the video clip according to a second timestamp of the recorded video wherein the first time stamp and second timestamp correspond to a same instance.

In example 5, the sensor information of any of examples 1 to 4 mayinclude a multiplicity of sensor data streams recorded from amultiplicity of sources concurrently with recording of the recordedvideo.

In example 6, the at least one set of sensor information of any ofexamples 1 to 5 may include wearable sensor data.

In example 7, the video clip creation module of any of examples 1 to 6may be to receive the sensor information, and to generate the video clipbased upon the sensor event when the sensor information matches apredetermined criterion.

In example 8, the video clip creation module of any of examples 1 to 7may be to generate the video clip based upon a predetermined relation toa time stamp of the sensor event.

In example 9, the video clip creation module of any of examples 1 to 8may be to predict an activity based upon the sensor event duringrecording of the video, and to generate a signal to adjust recording ofthe recorded video based upon the predicted activity.

In example 10, the video clip creation module of any of examples 1 to 9may be to activate video clip generation in accordance with a time ofday or user activity recorded in the recorded video.

In example 11, the video clip creation module of any of examples 1 to 10may be automatically direct transmission of a video clip to an externalsocial media site that is publicly accessible.

In example 12, the video clip creation module of any of examples 1 to 11may be to determine a source of the sensor information and scheduletransmission of the video clip to a target destination at a remotelocation based upon the source of the sensor information.

Example 13 includes at least one machine-readable storage mediumcomprising instructions that when executed by a computing device, causethe computing device to: store a recorded video; receive at least oneset of sensor information based on sensor data that is recordedconcurrently with the recorded video; and identify a sensor event fromthe at least one set of sensor information and to generate a video clipbased upon the sensor event, the video clip comprising video contentfrom the recorded video that is synchronized to the sensor event.

In example 14, the at least one machine-readable storage medium ofexample 13 may include instructions that when executed by a computingdevice, cause the computing device to identify a multiplicity of sensorevents from the sensor information and to generate a respectivemultiplicity of video clips from the recorded video that aresynchronized to the respective multiplicity of sensor events.

In example 15, the at least one machine-readable storage medium of anyof examples 13 to 14 may include instructions that when executed by acomputing device, cause the computing device to identify a first timestamp of sensor data associated with the sensor event and generate thevideo clip according to a second time stamp of the recorded videowherein the first time stamp and second time stamp correspond to a sameinstance.

In example 16, the at least one machine-readable storage medium of anyof examples 13 to 15 may include instructions that when executed by acomputing device, cause the computing device to receive the sensorinformation, and to generate the video clip based upon the sensor eventwhen the sensor information matches a predetermined criterion.

In example 17, the at least one machine-readable storage medium of anyof examples 13 to 16 may include instructions that when executed by acomputing device, cause the computing device to generate the video clipbased upon a predetermined relation to a time stamp of the sensor event.

In example 18, the at least one machine-readable storage medium of anyof examples 13 to 17 may include instructions that when executed by acomputing device, cause the computing device to predict an activitybased upon the sensor event during recording of the recorded video, andto generate a signal to adjust recording of the recorded video basedupon the predicted activity.

In example 19, the at least one machine-readable storage medium of anyof examples 13 to 18 may include instructions that when executed by acomputing device, cause the computing device to determine a source ofthe sensor information and schedule transmission of the video clip to atarget destination at a remote location based upon the source of thesensor information.

Example 20 is a computer implemented method that may include storing arecorded video; receiving at least one set of sensor informationcomprising sensor data that is recorded concurrently with the recordedvideo; identifying a sensor event from the at least one set of sensorinformation; and generating a video clip based upon the sensor event,the video clip comprising video content from the recorded video that issynchronized to the sensor event.

In example 21, the computer implemented method of example 20 may includeidentifying a multiplicity of sensor events from the sensor informationand generating a respective multiplicity of video clips from therecorded video that are synchronized to the respective multiplicity ofsensor events.

In example 22 the computer implemented method of any of examples 20 to21 may include identifying a first time stamp of sensor data associatedwith the sensor event and generating the video clip according to asecond time stamp of the recorded video wherein the first time stamp andsecond time stamp correspond to a same instance.

In example 23, the computer implemented method of any of examples 20 to22 may include receiving the sensor information, and generating thevideo clip based upon the sensor event when the sensor informationmatches a predetermined criterion.

In example 24, the computer implemented method of any of examples 20 to23 may include predicting an activity based upon the sensor event duringrecording of the recorded video, and generating a signal to adjustrecording of the recorded video based upon the predicted activity.

In example 25, the computer implemented method of any of examples 20 to24 may include determining a source of the sensor information andscheduling transmission of the video clip to a target destination at aremote location based upon the source of the sensor information.

Example 26 includes user equipment to automatically generate a videoclip comprising means to perform the method of any of examples 20-25.

Example 27 includes an apparatus to automatically generate a video clipcomprising means to perform the method of any one of examples 20-25.

In example 28, a system for automatically generating a video clip,includes a video recording component to record a video; a memory tostore the recorded video; an interface to receive at least one set ofsensor information based on sensor data that is recorded concurrentlywith the recorded video; and a video clip creation module to identify asensor event from the at least one set of sensor information and togenerate a video clip based upon the sensor event, where the video clipcomprises video content from the recorded video that is synchronized tothe sensor event.

In example 29, video clip creation module of example 28 may be toidentify a multiplicity of sensor events from the sensor information andto generate a respective multiplicity of video clips from the recordedvideo that are synchronized to the respective multiplicity of sensorevents.

In example 30, video clip creation module of any of examples 28 to 29may be to identify a first time stamp of sensor data associated with thesensor event and generate the video clip according to a second timestamp of the recorded video wherein the first time stamp and second timestamp correspond to a same instance.

In example 31, video clip creation module of any of examples 28 to 30may be to receive the sensor information, and to generate the video clipbased upon the sensor event when the sensor information matches apredetermined criterion.

In example 32, video clip creation module of any of examples 28 to 31may be to generate the video clip based upon a predetermined relation toa time stamp of the sensor event.

In example 33, video clip creation module of any of examples 28 to 32may be to predict an activity based upon the sensor event duringrecording of the video, and to generate a signal to adjust recording ofthe recorded video based upon the predicted activity.

In example 34, video clip creation module of any of examples 28 to 33may be to activate video clip generation in accordance with a time ofday or user activity recorded in the recorded video.

In example 35, video clip creation module of any of examples 28 to 34may be to automatically direct transmission of a video clip to anexternal social media host that is publicly accessible.

In example 36, video clip creation module of any of examples 28 to 35may be to determine a source of the sensor information and scheduletransmission of the video clip to a target destination at a remotelocation based upon the source of the sensor information.

The embodiments, as previously described, may be implemented usingvarious hardware elements, software elements, or a combination of both.Examples of hardware elements may include devices, logic devices,components, processors, microprocessors, circuits, processor circuits,circuit elements (e.g., transistors, resistors, capacitors, inductors,and so forth), integrated circuits, application specific integratedcircuits (ASIC), programmable logic devices (PLD), digital signalprocessors (DSP), field programmable gate array (FPGA), memory units,logic gates, registers, semiconductor device, chips, microchips, chipsets, and so forth. Examples of software elements may include softwarecomponents, programs, applications, computer programs, applicationprograms, system programs, software development programs, machineprograms, operating system software, middleware, firmware, softwaremodules, routines, subroutines, functions, methods, procedures, softwareinterfaces, application program interfaces (API), instruction sets,computing code, computer code, code segments, computer code segments,words, values, symbols, or any combination thereof. Determining whetheran embodiment is implemented using hardware elements and/or softwareelements may vary in accordance with any number of factors, such asdesired computational rate, power levels, heat tolerances, processingcycle budget, input data rates, output data rates, memory resources,data bus speeds and other design or performance constraints, as desiredfor a given implementation.

In some embodiments, an element is defined as a specific structureperforming one or more operations. It may be appreciated, however, thatany element defined as a specific structure performing a specificfunction may be expressed as a means or step for performing thespecified function without the recital of structure, material, or actsin support thereof, and such means or step is meant to cover thecorresponding structure, material, or acts described in the detaileddescription and equivalents thereof. The embodiments are not limited inthis context.

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Further, some embodiments may be described using the expression“coupled” and “connected” along with their derivatives. These terms arenot necessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

In addition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thusthe following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

What is claimed is:
 1. An apparatus, comprising: a memory to store arecorded video; an interface to receive at least one set of sensorinformation based on sensor data that is recorded concurrently with therecorded video; and a video clip creation module to identify a sensorevent from the at least one set of sensor information and to generate avideo clip based upon the sensor event, the video clip comprising videocontent from the recorded video that is synchronized to the sensorevent.
 2. The apparatus of claim 1, the sensor information comprisinganalyzed sensor data calculated from the sensor data.
 3. The apparatusof claim 1, the video clip creation module to identify a multiplicity ofsensor events from the sensor information and to generate a respectivemultiplicity of video clips from the recorded video that aresynchronized to the respective multiplicity of sensor events.
 4. Theapparatus of claim 1, the video clip creation module to identify a firsttime stamp of sensor data associated with the sensor event and generatethe video clip according to a second time stamp of the recorded videowherein the first time stamp and second time stamp correspond to a sameinstance.
 5. The apparatus of claim 1, the sensor information comprisinga multiplicity of sensor data streams recorded from a multiplicity ofsources concurrently with recording of the recorded video.
 6. Theapparatus of claim 1, the at least one set of sensor informationcomprising wearable sensor data.
 7. The apparatus of claim 1, the videoclip creation module to receive the sensor information, and to generatethe video clip based upon the sensor event when the sensor informationmatches a predetermined criterion.
 8. The apparatus of claim 1, thevideo clip creation module to generate the video clip based upon apredetermined relation to a time stamp of the sensor event.
 9. Theapparatus of claim 1, the video clip creation module to predict anactivity based upon the sensor event during recording of the video, andto generate a signal to adjust recording of the recorded video basedupon the predicted activity.
 10. The apparatus of claim 1, the videoclip creation module to activate video clip generation in accordancewith a time of day or activity recorded in the recorded video.
 11. Theapparatus of claim 1, the video clip creation module to automaticallydirect transmission of a video clip to an external social media sitethat is publicly accessible.
 12. The apparatus of claim 1, the videoclip creation module to determine a source of the sensor information andschedule transmission of the video clip to a target destination at aremote location based upon the source of the sensor information.
 13. Atleast one machine-readable storage medium comprising instructions thatwhen executed by a computing device, cause the computing device to:store a recorded video; receive at least one set of sensor informationbased on sensor data that is recorded concurrently with the recordedvideo; and identify a sensor event from the at least one set of sensorinformation and to generate a video clip based upon the sensor event,the video clip comprising video content from the recorded video that issynchronized to the sensor event.
 14. The at least one machine-readablestorage medium of claim 13 comprising instructions that when executed bya computing device, cause the computing device to identify amultiplicity of sensor events from the sensor information and togenerate a respective multiplicity of video clips from the recordedvideo that are synchronized to the respective multiplicity of sensorevents.
 15. The at least one machine-readable storage medium of claim 13comprising instructions that when executed by a computing device, causethe computing device to identify a first time stamp of sensor dataassociated with the sensor event and generate the video clip accordingto a second time stamp of the recorded video wherein the first timestamp and second time stamp correspond to a same instance.
 16. The atleast one machine-readable storage medium of claim 13 comprisinginstructions that when executed by a computing device, cause thecomputing device to receive the sensor information, and to generate thevideo clip based upon the sensor event when the sensor informationmatches a predetermined criterion.
 17. The at least one machine-readablestorage medium of claim 13 comprising instructions that when executed bya computing device, cause the computing device to generate the videoclip based upon a predetermined relation to a time stamp of the sensorevent.
 18. The at least one machine-readable storage medium of claim 13comprising instructions that when executed by a computing device, causethe computing device to predict an activity based upon the sensor eventduring recording of the recorded video, and to generate a signal toadjust recording of the recorded video based upon the predictedactivity.
 19. The at least one machine-readable storage medium of claim13 comprising instructions that when executed by a computing device,cause the computing device to determine a source of the sensorinformation and schedule transmission of the video clip to a targetdestination at a remote location based upon the source of the sensorinformation.
 20. A computer implemented method, comprising: storing arecorded video; receiving at least one set of sensor informationcomprising sensor data that is recorded concurrently with the recordedvideo; identifying a sensor event from the at least one set of sensorinformation; and generating a video clip based upon the sensor event,the video clip comprising video content from the recorded video that issynchronized to the sensor event.
 21. The computer implemented method ofclaim 20, comprising identifying a multiplicity of sensor events fromthe sensor information and generating a respective multiplicity of videoclips from the recorded video that are synchronized to the respectivemultiplicity of sensor events.
 22. The computer implemented method ofclaim 20, comprising identifying a first time stamp of sensor dataassociated with the sensor event and generating the video clip accordingto a second time stamp of the recorded video wherein the first timestamp and second time stamp correspond to a same instance.
 23. Thecomputer implemented method of claim 20, comprising receiving the sensorinformation, and generating the video clip based upon the sensor eventwhen the sensor information matches a predetermined criterion.
 24. Thecomputer implemented method of claim 20, comprising predicting anactivity based upon the sensor event during recording of the recordedvideo, and generating a signal to adjust recording of the recorded videobased upon the predicted activity.
 25. The computer implemented methodof claim 20, comprising determining a source of the sensor informationand scheduling transmission of the video clip to a target destination ata remote location based upon the source of the sensor information.